home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
BBS Toolkit
/
BBS Toolkit.iso
/
pc_board
/
gift4b12.zip
/
GIFTEST.LAB
< prev
next >
Wrap
Text File
|
1992-01-25
|
3KB
|
47 lines
GIFtest 4.0ß
CopyRight 1991 by Dave Navarro, Jr.
A number of users are reporting problems running GIFtest properly with
ZipLab Plus. Possible reasons for failure are:
■ You don't have the correct location and name for the description
file of each node in the CNF file. Please read the documentation
for an explanation of where to find the description file for the
BBS type you are running. Under no circumstances should you be
using the name of the description file for your entire Upload
directory. Both PCBoard and ProDoor use a special file for
"just uploaded" files that contain the descriptions. It's always
UPDESC for PCBoard (though PCB doesn't always keep it in the same
place for all BBS's, and with multiple nodes, PCB appends the node
number as the extension), and it's always $DOOR.NAM for ProDoor
(ProDoor keeps it in the same directory as your PCBOARD.DAT file
for each node).
The best solution to this problem is for Jeff to add another field
to ZipLab Plus asking if you want the resolution added to the
description. If the answer is yes then ZipLab would append the
command "/F:" with the proper name and location of the description
file to the GIFtest command line (which it knows since it reads
the information from PCBOARD.DAT). I've asked Jeff to do this,
but to date he hasn't. So bug him about it.
■ You have the wrong commands on the GIFtest command line in
PTEST.CFG for your BBS type. If it doesn't seem to be working
correctly, then put NONE for your GIFtest command line in PTEST.CFG
and see what happens. If it works, add one command at a time
until it fails again. If it still fails with no passes parameters
other than the filename from ZipLab, try running it in your
upload batch file outside of ZipLab and see if it fails. If
it still does, then let me know. If it doesn't, then either you
or ZipLab are doing something wrong.
A note to authors of other file testing programs that call GIFtest. The
majority of the problems associated with GIFtest and your program is due
to user error in setting up either GIFtest or your program. Generally
associated with inserting the GIF resolution into the description on
PCB and ProDoor BBS's. If you are having similar problems, I suggest
you shell to GIFtest to test the GIF, but add the resolution to the
description yourself. It would clear up a number of interface problems
and probably make your life easier.